Techniques for persistent memory virtualization

ABSTRACT

Examples may include techniques for persistent memory virtualization. Persistent memory maintained at one or more memory devices coupled with a host computing device may be allocated and assigned to a virtual machine (VM) hosted by the host computing device. The allocated persistent memory based on a file based virtual memory to be used by the VM. An extended page table (EPT) may be generated to map physical memory pages of the one or more memory devices to virtual logical blocks of the file based virtual memory. Elements of the VM then enumerate a presence of the assigned allocated persistent memory, create a virtual disk abstraction for the file based virtual memory and use the EPT to directly access the assigned allocated persistent memory.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.15/193,995, filed Jun. 27, 2016, entitled “TECHNIQUES FOR PERSISTENTMEMORY VIRTUALIZATION”, and is now U.S. Pat. No. 10,210,012. The entirespecification of which are hereby incorporated by reference in itsentirety.

TECHNICAL FIELD

Examples described herein are generally related to use of persistentmemory in a computing system.

BACKGROUND

Persistent memory may be characterized as a way to store data structuressuch that the data structures may continue to be accessible using memoryinstructions or memory application programming interfaces (APIs) evenafter the process that created or last modified the data structuresends. Persistent memory may be accessed in a similar manner to types ofvolatile memory used for system memory of a computing system (e.g.,dynamic random access memory (DRAM)), but it retains stored datastructures across power loss in a similar manner to computer storage(e.g., hard disk drives or solid state drives). Persistent memorycapabilities extend beyond an ability to retain stored data structuresacross power loss. For example, key metadata, such as page table entriesor other constructs that translate virtual addresses to physicaladdresses also need to be retained across power loss.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates an example first system.

FIG. 2 illustrates an example first extended page table for allocatedpersistent memory.

FIG. 3 illustrates an example first process.

FIG. 4 illustrates an example second system.

FIG. 5 illustrates an example second extended page table for allocatedpersistent memory.

FIG. 6 illustrates an example second process.

FIG. 7 illustrates an example apparatus.

FIG. 8 illustrates an example logic flow.

FIG. 9 illustrates an example storage medium.

FIG. 10 illustrates an example computing platform.

DETAILED DESCRIPTION

In some examples, application of persistent memory as a direct accessstorage (DAS) by an operating system (OS) may provide a relatively highspeed and low latency storage for software applications hosted orsupported by a computing device. However, possible performance benefitsof DAS may be lost when storage arranged for DAS is virtualized by avirtual machine monitor (VMM) of the hosting computing device. Also,current techniques to virtualize storage maintained by a host computingdevice for use by a guest OS to be executed or implemented by a virtualmachine (VM) hosted by the host computing device may use a file basedvirtual memory. The file based virtual memory may be similar to avirtual hard drive (VHD) or a virtual machine disk (VMDK). A file basedvirtual memory may be flexible and portable but has performanceconstraints (e.g., higher latencies) that reduce the benefits attributedto application of persistent memory as a DAS by the guest OS for the VM.

According to some examples, current technique for use of virtual memoryfor virtualized storage may use a file accessible to a host OS toprovide a virtual disk abstraction. The virtual memory file may bearranged to maintain a mapping of virtual logical blocks to a fileoffset and file blocks that back the virtual logical blocks. In someexamples, a storage access interface abstraction (e.g., small computersystem interface (SCSI) disk abstraction) may be exposed to the guestOS. Disk accesses generated by the guest OS or applications executed byVM may be routed through the VMM to the host OS. The host OS may thenlook up the mapping of the virtual logical block or blocks to file blockand then read/write the corresponding file block. These currenttechniques may provide at least some flexibility and portability in thatit may be possible to copy the file to another host computing device andattach to a different VM associated with that other host computingdevice. The virtual memory, in some examples, may be thinly provisionedsuch that file blocks backing the virtual logical volume are allocatedon demand. However this thinly provisioned technique has significantperformance overhead due to the need of the guest to send requests forallocation to the host and then receive allocations in response to therequests. Hence when the backing storage of the virtual memory is alsoarranged as a DAS volume for the guest OS for the VM, performancebenefits for using persistent memory for the DAS volume may not berealized by the guest OS for the VM.

FIG. 1 illustrates an example system 100. In some examples, as shown inFIG. 1, system 100 includes a host operating system (OS) 110, a virtualmachine (VM) 120, a virtual machine monitor (VMM) 130 and a persistentmemory 140. According to some examples, system 100 may be at least partof a host computing device that may include, but is not limited to, apersonal computer, a desktop computer, a laptop computer, a tablet, aserver, a server array or server farm, a web server, a network server,an Internet server, a work station, a mini-computer, a main framecomputer, a supercomputer, a network appliance, a web appliance, adistributed computing system, multiprocessor systems, processor-basedsystems, or combination thereof.

According to some examples, as shown in FIG. 1, host OS 110 may includea file system 112, a persistent memory disk driver 114 and a virtualdisk provider 116. As described in more detail below, these elements ofhost OS 110 may work in collaboration with VMM 130 to directly allocateor assign at least a portion of persistent memory 140 to create a filebased virtual memory for use by elements of VM 120. These elements of VM120 such as a file system 122 and a persistent memory disk driver 124for guest OS kernel 121 may be capable of directly accessing physicalblocks of persistent memory 140 backing the file based virtual memorythrough one or more extended page table(s) 132 maintained by VMM 130 toutilize the file based virtual memory. In this manner, the directaccessing of the physical blocks of persistent memory 140 backing thefile based virtual memory may result in the file based virtual memoryresiding on a DAS volume. Once the file based virtual memory residing onthe DAS volume is established, direct access by elements of VM 120 mayoccur without involvement of VMM 130 or host OS 110.

In some examples, persistent memory 140 may be composed of one or morememory devices which may include various types of volatile and/ornon-volatile memory. Volatile memory may include, but is not limited to,random-access memory (RAM), Dynamic RAM (D-RAM), double data ratesynchronous dynamic RAM (DDR SDRAM), static random-access memory (SRAM),thyristor RAM (T-RAM) or zero-capacitor RAM (Z-RAM). Non-volatile memorymay include, but is not limited to, non-volatile types of memory such as3-D cross-point memory that may be byte or block addressable. Theseblock addressable or byte addressable non-volatile types of memory mayinclude, but are not limited to, memory that uses chalcogenide phasechange material (e.g., chalcogenide glass), multi-threshold level NANDflash memory, NOR flash memory, single or multi-level phase changememory (PCM), resistive memory, nanowire memory, ferroelectrictransistor random access memory (FeTRAM), magnetoresistive random accessmemory (MRAM) memory that incorporates memristor technology, or spintransfer torque MRAM (STT-MRAM), or a combination of any of the above,or other non-volatile memory types.

According to some examples, the one or more memory devices included inpersistent memory 140 may be designed to operate in accordance withvarious memory technologies. The various memory technologies mayinclude, but are not limited to, DDR4 (DDR version 4, initialspecification published in September 2012 by JEDEC), LPDDR4 (LOW POWERDOUBLE DATA RATE (LPDDR) version 4, JESD209-4, originally published byJEDEC in August 2014), WIO2 (Wide I/O 2 (WideIO2), JESD229-2, originallypublished by JEDEC in August 2014), HBM (HIGH BANDWIDTH MEMORY DRAM,JESD235, originally published by JEDEC in October 2013), and/or othertechnologies based on derivatives or extensions of such specifications.The various memory technologies may also include memory technologiescurrently in development that may include, but are not limited to, DDR5(DDR version 5, currently in discussion by JEDEC), LPDDR5 (LPDDR version5, currently in discussion by JEDEC), HBM2 (HBM version 2, currently indiscussion by JEDEC), and/or other new technologies based on derivativesor extensions of these developing memory technologies.

In some examples, the one or more memory devices may be located on oneor more dual in-line memory modules (DIMMs) coupled with a hostcomputing device that may host the elements of system 100 shown inFIG. 1. These DIMMs may be designed to function as a registered DIMM(RDIMM), a load reduced DIMM (LRDIMM), a fully-buffered DIMM (FB-DIMM),an unbuffered DIMM (UDIMM) or a small outline (SODIMM). Examples are notlimited to only these DIMM designs.

According to some examples, memory devices of persistent memory 140maintained on one or more DIMMs may include all or combinations of typesof volatile or non-volatile memory. For example, memory devices of afirst type of DIMM may include volatile memory on a front or first sideand may include non-volatile memory on a back or second side. In otherexamples, a second type of DIMM may include combinations of non-volatileand volatile types of memory on either side of this second type of DIMM.In other examples, all memory devices on a given DIMM may be eithervolatile types of memory or non-volatile types of memory. In otherexamples, a third type of DIMM may include non-volatile memory and atleast some volatile memory and this third type of DIMM may be referredto as a non-volatile DIMM (NVDIMM).

FIG. 2 illustrates example allocations 200. In some examples, as shownin FIG. 2, allocations 200 includes a two-level extended page table(EPT) 132. Although this disclosure contemplates use of othermulti-level EPTs, for simplicity a two-level EPT is shown and described.The two-level EPT 132 may include page directory entry (PDE) table 210and page table entry (PTE) tables 212 and 214. According to someexamples, VMM 130 may work in cooperation with host OS 110 to create EPT132 to facilitate direct access to allocated physical memory pages 235maintained at memory device(s) 230 of persistent memory 140.

According to some examples, as described more below, allocated physicalmemory pages 235 may include physical blocks of persistent memory 140for a file based virtual memory residing on a DAS volume. For theseexamples, allocated physical memory pages 235 may have been directlyassigned or allocated to VM 120. The two-level EPT 132 may function as amapping of virtual logical blocks to physical blocks of persistentmemory 140 included within physical memory pages 235. Once physicalmemory pages 235 are assigned or allocated, elements of VM 120 may useEPT 132 to directly access persistent memory 140 without involvement ofVMM 130 or host OS 110 during these direct accesses to persistent memory140.

FIG. 3 illustrates an example process 300. In some examples, process 300may be for initiating, using and shutting down a file based virtualmemory residing on a DAS volume that is backed by a persistent memory.For these examples, elements of system 100 as shown in FIG. 1 such ashost OS 110, VM 120, VMM 130 or persistent memory (PM) 140 may berelated to process 300. Allocations 200 as shown in FIG. 2 may also berelated to process 300. However, example process 300 is not limited toimplementations using elements of system 100 or allocations 200 shown inFIGS. 1-2.

Beginning at process 3.1 (Allocate PM), logic and/or features of host OS110 may allocate physical blocks and/or pages of PM 140 for use in afile based virtual memory utilized by VMs managed or controlled by VMM130. In some examples, persistent memory disk driver 114 of host OS 110may allocate the physical blocks of PM 140. For these examples,allocations of physical blocks of PM 140 may be based on, but is notlimited to, available blocks of PM 140 at time of initialization of theVMs managed or controlled by VMM 130.

Moving to process 3.2 (Coordinate/Assign allocated PM to VM), logicand/or features of VMM 130 may coordinate with elements of Host OS 110to assign allocated PM to VM 120. According to some examples, virtualdisk provider 116 may interpret a file based virtual memory for use byelements of VM 120 to determine what physical blocks and/or pages of PM140 need to be directly allocated to VM 120. VMM 130 may then create oneor more EPT tables such as EPT 132 that may map to physical memory pages235 maintained by one or more memory device(s) 230 of persistent memory140 to virtual logical blocks of the file based virtual memoryinterpreted by virtual disk provider 116. EPT 132, for example, may becreated according to allocations 200 mentioned above for FIG. 2.

Moving to process 3.3 (BIOS to Enumerate Presence of PM), logic and/orfeatures of VM 120 may include a guest basic input/output system (BIOS)capable of enumerating a presence of PM allocated to VM 120. In someexamples, the guest BIOS may be capable of enumerating the presence ofPM allocated to VM 120 via VMM 130 indicating presence of an AdvancedConfiguration and Power Interface (ACPI) table that provides informationto enumerate persistent memory that has been allocated to VM 120. TheACPI table may be according to the ACPI specification, version 6.1,published by the Unified Extensible Firmware Interface (UEFI) Forum inJanuary of 2016 (“the ACPI specification”), and/or other derivatives orextensions of the ACPI specification. For example, the memory devices ofPM 140 may be maintained on one or more NVDIMMs and the ACPI table maybe an NVDIMM firmware interface table (NFIT) that provides informationto the guest BIOS. For this example, the guest BIOS may determine thatphysical memory page(s) 235 of PM 140 have been mapped to virtuallogical blocks of the file based virtual memory interpreted by virtualdisk provider 116 based on the NFIT.

Moving to process 3.4 (Instantiate PM Stack to Create Virtual DiskAbstraction), logic and/or features of VM 120 such as file system 122 ofguest OS kernel 121 may be capable of instantiating a PM stack to createa virtual disk abstraction exposed by the information provided in theACPI table (e.g., NFIT).

Moving to process 3.5 (Direct Access using EPT(s)), logic and/orfeatures of VM 120 such as persistent memory disk driver 124 of guest OSkernel 121 may be capable of direct access to PM 140 using EPT(s) 132.In some examples, the guest BIOS may setup persistent memory disk driver124 to use EPT 132 to directly access physical memory page(s) 235following enumeration of the presence of PM allocated to VM 120. Forthese examples, requests by file system 122 to access data maintained invirtual logical blocks of a file based virtual memory may be fulfilledby persistent memory disk driver 124 directly accessing PM 140 via useof EPT 132 without a need for further involvement of VMM 130 or host OS110.

Moving to process 3.6 (Shutdown VM), logic and/or features of VMM 130and host OS 110 may determine to shut down VM 120. For example, VM 120may be shutdown to migrate VM 120 to another host computing device.

Moving to process 3.7 (Generate File from Allocated PM), logic and/orfeatures of host OS 110 may generate a file from data maintained inmemory page(s) 235 of PM 140. In some examples, once VM 120 is shutdown,the file based virtual memory seen by virtual disk provider 116 and/orfile system 112 may be up-to-date since memory page(s) 235 backing thefile based virtual memory are the same memory page(s) 235 for thevirtual disk abstraction used by file system 122 of guest OS kernel 121while VM 120 was in operation.

Moving to process 3.8 (Copy File to Another Host), logic and/or featuresof host OS 110 may copy the file generated from data maintained inmemory page(s) 235 of PM 140 to another host computing device. In someexamples, once the file is copied, memory page(s) 235 may bere-allocated or re-assigned to another VM.

FIG. 4 illustrates an example system 400. In some examples, as shown inFIG. 4, system 400 is similar to system 100 shown in FIG. 1 and includesa host OS 410, a VM 420, a VMM 130 and a persistent memory 440.According to some examples, rather than allocating most if not allpersistent memory pages backing up a file based virtual memory duringinitialization of a VM as described above for FIGS. 1-3, the file basedvirtual memory may be thinly provisioned. In other words, thinlyprovisioned file based virtual memory supported by system 400 mayallocate at least some persistent memory pages on demand.

According to some examples, as shown in FIG. 4, host OS 410 may includea file system 412, a persistent memory disk driver 414 and a virtualdisk provider 416. As described in more detail below, these elements ofhost OS 410 may work in collaboration with VMM 430 to initially directlyallocate or assign at least a portion of persistent memory 440 to createa thinly provisioned file based virtual memory for initial use byelements of VM 420. These elements of VM 420 such as a file system 422and a persistent memory disk driver 424 for guest OS kernel 421 may becapable of directly accessing physical blocks of persistent memory 140backing the virtual memory through one or more extended page table(s)432 maintained by VMM 430 to utilize the thinly provisioned file basedvirtual memory. Similar to system 100, the direct accessing of thephysical blocks of persistent memory 440 backing the thinly provisionedfile based virtual memory may result in the thinly file based virtualmemory residing on a DAS volume. Once the thinly provisioned file basedvirtual memory residing on the DAS volume is established, direct accessby elements of VM 120 may occur without involvement of VMM 130 or hostOS 110 for the initially allocated physical memory pages of persistentmemory 140. However, as described more below, an on-demand allocationmay be communicated via a virtual interconnect 434 between virtual diskprovider 426 and persistent memory disk driver 424. Virtual interconnect434 is shown in FIG. 4 as a dashed line to indicate that the on-demandallocation may be needed for just a first access to a virtual logicalblock that is to be backed up by the on-demand allocation.

FIG. 5 illustrates example allocations 501 and 502. In some examples, asshown in FIG. 5, allocations 501 and 502 may each include a two-levelextended page table (EPT) 432 similar to EPT 132 shown in FIG. 2. Atwo-level EPT 432 may include PDE table 510 and PTE tables 512 and 514.According to allocations 501 (pre-request), VMM 430 may work incooperation with host OS 410 to create EPT 432 to first facilitatedirect access to allocated physical memory page 535 maintained at memorydevice(s) 430 of persistent memory 440 prior to an on-demand allocationrequest. VMM 430 may also work in cooperation with host OS 410 to modifyor update EPT 432 to then facilitate direct access to additionallyallocated physical memory pages 536 after an on-demand allocationrequest according to allocations 502 (post-request).

According to some examples, as described more below, allocated physicalmemory page 435 may include physical blocks of persistent memory 440 fora thinly provisioned file based virtual memory residing on a DAS volume.For these examples, allocated physical memory page 435 may have beendirectly assigned or allocated to VM 120 when initialized. Similar toEPT 132, the two-level EPT 432 may function as a mapping of virtuallogical blocks to physical blocks of persistent memory 440 includedwithin physical memory page 535. Once physical memory page 535 isassigned or allocated, elements of VM 120 may use EPT 432 to directlyaccess this physical memory page without involvement of VMM 430 or host410 during these direct accesses to persistent memory 440.

In some examples, as described more below, allocated physical memorypages 536 may include additional physical blocks of persistent memory440 for the thinly provisioned file based virtual memory residing on theDAS volume that may be expanded when access to virtual logical blocksnot initially mapped in EPT 432 is needed (e.g., by file system 122).For these examples, allocated physical memory pages 536 may includeadditional physical memory pages that may be directly assigned orallocated to VM 120 on demand. EPT 432 may be updated to map these newlyaccessed virtual logical blocks to newly allocated physical blocks ofpersistent memory 440 included within physical memory pages 536 (e.g.,P2 and/or P3). Once physical memory pages 536 are assigned or allocated,elements of VM 120 may use the updated EPT 432 to directly access thesephysical memory pages without involvement of VMM 430 or host 410 duringthese direct accesses to persistent memory 440.

FIG. 6 illustrates an example process 600. In some examples, process 600may be for initiating, using and shutting down a thinly provisioned filebased virtual memory residing on a DAS volume that is backed by apersistent memory. For these examples, elements of system 400 as shownin FIG. 4 such as host OS 410, VM 420, VMM 430 or persistent memory (PM)440 may be related to process 600. Allocations 500 as shown in FIG. 5may also be related to process 600. However, example process 600 is notlimited to implementations using elements of system 400 or allocations500 shown in FIGS. 4-5.

Beginning at process 6.1 (Allocate PM), logic and/or features of host OS410 may allocate physical blocks and/or pages of PM 440 for use in athinly provisioned file based virtual memory utilized by VMs managed orcontrolled by VMM 430. In some examples, persistent memory disk driver414 of host OS 410 may allocate the physical blocks of PM 440. For theseexamples, initial allocations of physical blocks of PM 440 may be basedon, but is not limited to, available blocks of PM 440 at time ofinitialization of the VMs managed or controlled by VMM 430.

Moving to process 6.2 (Coordinate/Assign allocated PM to VM), logicand/or features of VMM 430 may coordinate with elements of Host OS 410to assign initially allocated PM to VM 420. According to some examples,virtual disk provider 416 may interpret a file based virtual memory foruse by elements of VM 420 to determine what physical blocks and/or pagesof PM 440 need to be directly allocated to VM 420 upon initialization.VMM 430 may then create one or more EPT tables such as EPT 432 that maymap to physical memory page 535 maintained by one or more memorydevice(s) 530 of persistent memory 440 to virtual logical blocks of thefile based virtual memory interpreted by virtual disk provider 416. EPT432, for example, may be created according to allocations 500 mentionedabove for FIG. 5.

Moving to process 6.3 (BIOS to Enumerate Presence of PM), logic and/orfeatures of VM 420 may include a guest BIOS capable of enumeratingpresence of PM allocated to VM 420. In some examples, the guest BIOS mayhave been capable of enumerating presence of PM allocated to VM 420 viaVMM 430 indicating presence of an ACPI table that provides informationto enumerate persistent memory that has been allocated and assigned toVM 420. For examples, the ACPI table may be according to the ACPIspecification and memory devices of PM 440 may be maintained on one ormore NVDIMMs and the ACPI table may be an NFIT that provides informationto the guest BIOS. For this example, the guest BIOS may determine thatphysical memory page 535 of PM 440 has been mapped to virtual logicalblocks of the file based virtual memory interpreted by virtual diskprovider 416 based on the NFIT.

Moving to process 6.4 (Instantiate PM Stack to Create Virtual DiskAbstraction), logic and/or features of VM 420 such as file system 422 ofguest OS kernel 421 may be capable of instantiating a PM stack to createa virtual disk abstraction exposed by the information provided in theACPI table (e.g., NFIT).

Moving to process 6.5 (Direct Access using EPT), logic and/or featuresof VM 420 such as persistent memory disk driver 424 of guest OS kernel421 may be capable of direct access to PM 440 using EPT 432. In someexamples, the guest BIOS may setup persistent memory disk driver 424 touse EPT 432 to directly access physical memory page 535 followingenumeration of the presence of PM allocated to VM 420. For theseexamples, requests by file system 422 to access data maintained invirtual logical blocks of a file based virtual memory may be fulfilledby persistent memory disk driver 424 directly accessing PM 440 via useof EPT 432 without a need for further involvement of VMM 430 or host OS410 as long as those virtual logical blocks are mapped to physicalmemory page 535.

Moving to process 6.6 (Access to Virtual Block(s) not Mapped to PhysicalMemory Page), file system 422 may request access to one or more virtuallogical blocks not physically mapped to physical memory page 535. Inother words, memory pages from PM 440 have yet to be allocated to VM 420for direct access.

Moving to process 6.7 (Request PM Allocation), logic and/or features ofVM 420 may place a request to host OS 410 for an on-demand allocation ofadditional memory pages. In some examples, the request may be madethrough virtual interconnect 434 between virtual disk provider 416 andpersistent memory disk driver 424.

Moving to process 6.8 (Allocate Additional PM), logic and/or features ofhost OS 410 may indicate an allocation of additional PM to VMM 430 thatincludes memory pages 536.

Moving to process 6.9 (Assign Additional PM and Update EPT), logicand/or features of VMM 430 may update EPT 432 that may map the virtuallogical block(s) to the newly allocated PM that includes memory pages536.

Moving to process 6.10 (Update Virtual Disk Abstraction), logic and/orfeatures of VM 420 such as file system 422 may update the virtual diskabstraction based on the updated EPT.

Moving to process 6.11 (Direct Access using Updated EPT), logic and/orfeatures of VM 420 such as persistent memory disk driver 424 of guest OSkernel 421 may be capable of direct access to PM 440 using updated EPT432. For these examples, requests by file system 422 to access datamaintained in virtual logical blocks of a thinly provisioned file basedvirtual memory may be fulfilled by persistent memory disk drive 424directly accessing PM 440 via use of the updated EPT 432 without a needfor further involvement of VMM 430 or host OS 410 as long as thosevirtual logical blocks are mapped to physical memory pages 536.

Moving to process 6.12 (Shutdown VM), logic and/or features of VMM 430and host OS 410 may determine to shut down VM 420. For example, VM 420may be shutdown to migrate VM 420 to another host computing device.

Moving to process 6.13 (Generate File from Allocated PM), logic and/orfeatures of host OS 410 may generate a file from data maintained inmemory page(s) 535 of PM 440. In some examples, once VM 420 is shutdown,the file based virtual memory seen by virtual disk provider 416 and/orfile system 412 may be up-to-date since memory pages 536 backing thethinly provisioned file based virtual memory are the same memory pagesfor the virtual disk abstraction used by file system 422 of guest OSkernel 421 while VM 420 was in operation.

Moving to process 6.14 (Copy File to Another Host), logic and/orfeatures of host OS 410 may copy the file generated from data maintainedin memory pages 536 of PM 440 to another host computing device. In someexamples, once the file is copied, memory pages 536 may be re-allocatedor re-assigned to another VM. The process may then come to an end.

FIG. 7 illustrates an example block diagram for an apparatus 700.Although apparatus 700 shown in FIG. 7 has a limited number of elementsin a certain topology, it may be appreciated that the apparatus 700 mayinclude more or less elements in alternate topologies as desired for agiven implementation.

The apparatus 700 may be supported by circuitry 720 and may bemaintained or located at a host computing device and may be arranged toexecute or implement elements of a system such as system 100 or system400 shown in FIG. 1 or 4 and described above. Circuitry 720 may bearranged to execute one or more software or firmware implementedcomponents or logic 722-a. It is worthy to note that “a” and “b” and “c”and similar designators as used herein are intended to be variablesrepresenting any positive integer. Thus, for example, if animplementation sets a value for a=3, then a complete set of software orfirmware for components or logic 722-a may include components or logic722-1, 722-2 or 722-3. The examples presented are not limited in thiscontext and the different variables used throughout may represent thesame or different integer values. Also, these “components” or “logic”may be software/firmware stored in computer-readable media, and althoughthe components are shown in FIG. 7 as discrete boxes, this does notlimit these components to storage in distinct computer-readable mediacomponents (e.g., a separate memory, etc.).

According to some examples, circuitry 720 may include a processor orprocessor circuitry to implement logic and/or features that mayinitiate, use and shut down a file based virtual memory residing on aDAS volume that is backed by a persistent memory. The processor orprocessor circuitry can be any of various commercially availableprocessors, including without limitation an AMD® Athlon®, Duron® andOpteron® processors; ARM® application, embedded and secure processors;IBM® and Motorola® DragonBall® and PowerPC® processors; IBM and Sony®Cell processors; Intel® Atom®, Celeron®, Core (2) Duo®, Core i3, Corei5, Core i7, Itanium®, Pentium®, Xeon®, Xeon Phi® and XScale®processors; and similar processors. According to some examples circuitry720 may also be an application specific integrated circuit (ASIC) and atleast some components or logic 722-a may be implemented as hardwareelements of the ASIC. In some examples, circuitry 720 may also include afield programmable gate array (FPGA) and at least some logic 722-a maybe implemented as hardware elements of the FPGA.

According to some examples, apparatus 700 may include a host OScomponent 722-1. Host OS component 722-1 may be executed by circuitry720 to allocate persistent memory maintained at one or more memorydevices coupled with the host computing device to one or more VMs hostedby the host computing device based on respective file based virtualmemory to be used by the one or more VMs. For these examples, theallocation of persistent memory may be responsive to VMinitialization(s) 710. PM allocations 724-a may be maintained by Host OScomponent 722-1 (e.g., in a data structure such as a lookup table (LUT))to track what portions of persistent memory have been allocated to VMshosted by a computing device that includes apparatus 700.

In some examples, apparatus 700 may also include a VMM component 722-2.VMM component 722-2 may be executed by circuitry 720 to assign at leasta portion of the allocated persistent memory to a VM from among the oneor more VMs by creating an EPT to map at least one physical memory pagemaintained by at least one of the memory devices to first virtuallogical blocks of a file based virtual memory to be used by the VM. Forthese examples, VM PM assignments 724-c may be maintained by VMMcomponent 722-2 to track what portions of allocated persistent memoryhave been assigned to which of the one or more VMs. In some examples, VMPM assignments 724-c may include ACPI tables such as NFITs for use bythe one or more VMs to enumerate persistent memory allocated andassigned to the one or more VMs. Also, EPT information 724-d may bemaintained by VMM component 722-2 and may include the created EPT forthe VM from among the one or more VMs. VM PM assignments 724-c or EPTinformation 724-d may be maintain in a data structure such as LUT thatmay be accessible to other components of circuitry 720. For example, atleast some information included in EPT information 724-d may beaccessible to elements of the VM to access the created EPT.

According to some examples, apparatus 700 may also include a VMcomponent 722-3. VM component 722-3 may be executed by circuitry 720 toenumerate or determine a presence of the assigned allocated persistentmemory for the VM (e.g., based on information provided in an ACPI tablesuch as an NFIT), create a virtual disk abstraction for the file basedvirtual memory and enable the VM to use the EPT to directly access theassigned allocated persistent memory.

In some examples, VM component 722-3 may include a guest BIOS (notshown). The guest BIOS may be capable of enumerating the presence of theassigned allocated persistent memory. VM component 722-3 may maintain PMenumeration 724-e (e.g., in a LUT) and store the enumeration informationfor the assigned allocated persistent memory in PM enumeration 742-e.

According to some examples, VM component 722-3 may also include a guestOS kernel (not shown) capable of creating the virtual disk abstractionfor the file based virtual memory. VM component 722-3 may maintain thecreated virtual disk abstraction with virtual disk abstraction 724-f(e.g., in a LUT). The guest OS kernel may also have access to EPTinformation 724-d maintained by VMM component 722-2 to use the EPTcreated for the VM in order to directly access the assigned allocatedpersistent memory.

In some examples, VMM component 722-2 may cause the VM hosted by thecomputing device including apparatus 700 to shut down responsive to VMshutdown(s) 715. The reason for the shutdown may be to migrate the VM toanother or second host computing device. For these examples host OScomponent 722-1 may generate a file from data stored to the assignedallocated persistent memory. This file may be at least temporarilymaintained with VM files 724-b (e.g., to a data structure stored tosystem memory). Host OS component 722-1 may then cause a copy of thefile to be stored at a second host computing device arranged to supportthe VM via copied file(s) 730. The copied file included in copiedfile(s) 730 may enable the VM to resume operation on the second hostcomputing device while maintaining the same operating state prior tobeing shut down at the host computing device that includes apparatus700.

According to some examples, the file based virtual memory for use by theVM may be a thinly provisioned file based virtual memory (e.g., asdescribed for process 600). VM component 722-3 may request an additionalallocation of persistent memory responsive to the VM accessing secondvirtual logical blocks not mapped to the at least one physical memorypage maintained by at least one of the memory devices. For theseexamples, VMM component 722-2 may receive an indication that host OScomponent 722-1 has allocated the additional persistent memoryresponsive to the request. VMM component 722-2 may then assign theadditional allocation of persistent memory to the VM and update the EPTto map at least one additional physical memory page maintained by the atleast one of the memory devices to the second virtual logical blocks ofthe thinly provisioned filed based virtual memory. VM component 722-3may then update the virtual disk abstraction for the thinly provisionedfile based virtual memory and enable the VM to use the updated EPT todirectly access the assigned additionally allocated persistent memory.

FIG. 8 illustrates an example logic flow 800. As shown in FIG. 8 thefirst logic flow includes a logic flow 800. Logic flow 800 may berepresentative of some or all of the operations executed by one or morelogic, features, or devices described herein, such as apparatus 700.More particularly, logic flow 800 may be implemented by host OScomponent 722-1, VMM component 722-2 or VM component 722-3.

According to some examples, logic flow 800 at block 802 may receive anallocation of persistent memory maintained at one or more memory devicescoupled with a host computing device, the persistent memory allocated toone or more VMs hosted by the host computing device based on respectivefile based virtual memory to be used by the one or more VMs. For theseexamples, VMM component 722-2 may have received the allocation from hostOS component 722-1.

In some examples, logic flow 800 at block 804 may assign at least aportion of the allocated persistent memory to a VM from among the one ormore VMs by creating an EPT to map at least one physical memory pagemaintained by at least one of the memory devices to first virtuallogical blocks of a file based virtual memory to be used by the VM. Forthese example, VMM component 722-2 may assign the allocated persistentmemory to the VM and create the EPT.

According to some examples, logic flow 800 at block 806 may provideinformation to the VM for the VM to enumerate a presence of the assignedallocated persistent memory, create a virtual disk abstraction for thefile based virtual memory and use the EPT to directly access theassigned allocated persistent memory. For these examples, VMM component722-2 may provide the information to VM component 722-3 (e.g., in anACPI table such as an NFIT). VM component 722-3 may enumerate thepresence of the assigned allocated persistent memory, create a virtualdisk abstraction for the file based virtual memory and use the EPT todirectly access the assigned allocated persistent memory.

In some examples, logic flow 800 at block 808 may cause the VM to shutdown. For these examples, VMM component 722-2 may cause the VM to shutdown.

According to some examples, logic flow 800 at block 810 may generate afile from data stored to the assigned allocated persistent memory. Forthese examples, host OS component 722-1 may generate the file.

In some examples, logic flow 800 at block 812 may copy the file to asecond host computing device arranged to support the VM. For theseexamples, host OS component 722-1 may copy the file.

FIG. 9 illustrates an example storage medium 900. As shown in FIG. 9,the first storage medium includes a storage medium 900. The storagemedium 900 may comprise an article of manufacture. In some examples,storage medium 900 may include any non-transitory computer readablemedium or machine readable medium, such as an optical, magnetic orsemiconductor storage. Storage medium 900 may store various types ofcomputer executable instructions, such as instructions to implementlogic flow 800. Examples of a computer readable or machine readablestorage medium may include any tangible media capable of storingelectronic data, including volatile memory or non-volatile memory,removable or non-removable memory, erasable or non-erasable memory,writeable or re-writeable memory, and so forth. Examples of computerexecutable instructions may include any suitable type of code, such assource code, compiled code, interpreted code, executable code, staticcode, dynamic code, object-oriented code, visual code, and the like. Theexamples are not limited in this context.

FIG. 10 illustrates an example computing platform 1000. In someexamples, as shown in FIG. 10, computing platform 1000 may include aprocessing component 1040, other platform components 1050 or acommunications interface 1060. According to some examples, computingplatform 1000 may be a host computing device capable of hosting orsupporting one or more VMs.

According to some examples, processing component 1040 may executeprocessing operations or logic for apparatus 700 and/or storage medium900. Processing component 1040 may include various hardware elements,software elements, or a combination of both. Examples of hardwareelements may include devices, logic devices, components, processors,microprocessors, circuits, processor circuits, circuit elements (e.g.,transistors, resistors, capacitors, inductors, and so forth), integratedcircuits, application specific integrated circuits (ASIC), programmablelogic devices (PLD), digital signal processors (DSP), field programmablegate array (FPGA), memory units, logic gates, registers, semiconductordevice, chips, microchips, chip sets, and so forth. Examples of softwareelements may include software components, programs, applications,computer programs, application programs, device drivers, systemprograms, software development programs, machine programs, operatingsystem software, middleware, firmware, software modules, routines,subroutines, functions, methods, procedures, software interfaces,application program interfaces (API), instruction sets, computing code,computer code, code segments, computer code segments, words, values,symbols, or any combination thereof. Determining whether an example isimplemented using hardware elements and/or software elements may vary inaccordance with any number of factors, such as desired computationalrate, power levels, heat tolerances, processing cycle budget, input datarates, output data rates, memory resources, data bus speeds and otherdesign or performance constraints, as desired for a given example.

In some examples, other platform components 1050 may include commoncomputing elements, such as one or more processors, multi-coreprocessors, co-processors, memory units, chipsets, controllers,peripherals, interfaces, oscillators, timing devices, video cards, audiocards, multimedia input/output (I/O) components (e.g., digitaldisplays), power supplies, and so forth. Examples of memory units mayinclude without limitation various types of computer readable andmachine readable storage media in the form of one or more higher speedmemory units, such as read-only memory (ROM), RAM, DRAM, DDR DRAM,synchronous DRAM (SDRAM), DDR SDRAM, SRAM, programmable ROM (PROM),EPROM, EEPROM, flash memory, ferroelectric memory, SONOS memory, polymermemory such as ferroelectric polymer memory, nanowire, FeTRAM or FeRAM,ovonic memory, phase change memory, memristors, STT-MRAM, magnetic oroptical cards, an array of devices such as Redundant Array ofIndependent Disks (RAID) drives, solid state memory devices (e.g., USBmemory), solid state drives (SSD) and any other type of storage mediasuitable for storing information. In some examples, these types ofmemory units may be arranged as persistent memory and may be maintainedin one or more DIMMs.

In some examples, communications interface 1060 may include logic and/orfeatures to support a communication interface. For these examples,communications interface 860 may include one or more communicationinterfaces that operate according to various communication protocols orstandards to communicate over direct or network communication links.Direct communications may occur via use of communication protocols suchas SMBus, PCIe, NVMe, QPI, SATA, SAS or USB communication protocols.Network communications may occur via use of communication protocols orstandards related to IEEE 802.3, iWARP, Infiniband, RoCE, SATA, SCSI,SAS. Network communication may also occur according to one or moreOpenFlow specifications such as the OpenFlow Hardware Abstraction APISpecification.

Computing platform 1000 may be part of a host computing device that maybe, for example, user equipment, a computer, a personal computer (PC), adesktop computer, a laptop computer, a notebook computer, a netbookcomputer, a tablet, a smart phone, embedded electronics, a gamingconsole, a server, a server array or server farm, a web server, anetwork server, an Internet server, a work station, a mini-computer, amain frame computer, a supercomputer, a network appliance, a webappliance, a distributed computing system, multiprocessor systems,processor-based systems, or combination thereof. Accordingly, functionsand/or specific configurations of computing platform 1000 describedherein, may be included or omitted in various embodiments of computingplatform 1000, as suitably desired.

The components and features of computing platform 1000 may beimplemented using any combination of discrete circuitry, ASICs, logicgates and/or single chip architectures. Further, the features ofcomputing platform 1000 may be implemented using microcontrollers,programmable logic arrays and/or microprocessors or any combination ofthe foregoing where suitably appropriate. It is noted that hardware,firmware and/or software elements may be collectively or individuallyreferred to herein as “logic”, “feature”, “component”, “circuit” or“circuitry.”

One or more aspects of at least one example may be implemented byrepresentative instructions stored on at least one machine-readablemedium which represents various logic within the processor, which whenread by a machine, computing device or system causes the machine,computing device or system to fabricate logic to perform the techniquesdescribed herein. Such representations may be stored on a tangible,machine readable medium and supplied to various customers ormanufacturing facilities to load into the fabrication machines thatactually make the logic or processor.

Various examples may be implemented using hardware elements, softwareelements, or a combination of both. In some examples, hardware elementsmay include devices, components, processors, microprocessors, circuits,circuit elements (e.g., transistors, resistors, capacitors, inductors,and so forth), integrated circuits, ASICs, PLDs, DSPs, FPGAs, memoryunits, logic gates, registers, semiconductor device, chips, microchips,chip sets, and so forth. In some examples, software elements may includesoftware components, programs, applications, computer programs,application programs, system programs, machine programs, operatingsystem software, middleware, firmware, software modules, routines,subroutines, functions, methods, procedures, software interfaces, APIs,instruction sets, computing code, computer code, code segments, computercode segments, words, values, symbols, or any combination thereof.Determining whether an example is implemented using hardware elementsand/or software elements may vary in accordance with any number offactors, such as desired computational rate, power levels, heattolerances, processing cycle budget, input data rates, output datarates, memory resources, data bus speeds and other design or performanceconstraints, as desired for a given implementation.

Some examples may include an article of manufacture or at least onecomputer-readable medium. A computer-readable medium may include anon-transitory storage medium to store logic. In some examples, thenon-transitory storage medium may include one or more types ofcomputer-readable storage media capable of storing electronic data,including volatile memory or non-volatile memory, removable ornon-removable memory, erasable or non-erasable memory, writeable orre-writeable memory, and so forth. In some examples, the logic mayinclude various software elements, such as software components,programs, applications, computer programs, application programs, systemprograms, machine programs, operating system software, middleware,firmware, software modules, routines, subroutines, functions, methods,procedures, software interfaces, API, instruction sets, computing code,computer code, code segments, computer code segments, words, values,symbols, or any combination thereof.

According to some examples, a computer-readable medium may include anon-transitory storage medium to store or maintain instructions thatwhen executed by a machine, computing device or system, cause themachine, computing device or system to perform methods and/or operationsin accordance with the described examples. The instructions may includeany suitable type of code, such as source code, compiled code,interpreted code, executable code, static code, dynamic code, and thelike. The instructions may be implemented according to a predefinedcomputer language, manner or syntax, for instructing a machine,computing device or system to perform a certain function. Theinstructions may be implemented using any suitable high-level,low-level, object-oriented, visual, compiled and/or interpretedprogramming language.

Some examples may be described using the expression “in one example” or“an example” along with their derivatives. These terms mean that aparticular feature, structure, or characteristic described in connectionwith the example is included in at least one example. The appearances ofthe phrase “in one example” in various places in the specification arenot necessarily all referring to the same example.

Some examples may be described using the expression “coupled” and“connected” along with their derivatives. These terms are notnecessarily intended as synonyms for each other. For example,descriptions using the terms “connected” and/or “coupled” may indicatethat two or more elements are in direct physical or electrical contactwith each other. The term “coupled,” however, may also mean that two ormore elements are not in direct contact with each other, but yet stillco-operate or interact with each other.

The follow examples pertain to additional examples of technologiesdisclosed herein.

Example 1

An example apparatus may include circuitry at a host computing device.The apparatus may also include a host OS component for execution by thecircuitry to allocate persistent memory maintained at one or more memorydevices coupled with the host computing device to one or more VMs hostedby the host computing device based on respective file based virtualmemory to be used by the one or more VMs. The apparatus may also includea VMM component for execution by the circuitry to assign at least aportion of the allocated persistent memory to a VM from among the one ormore VMs by creating an EPT to map at least one physical memory pagemaintained by at least one of the memory devices to first virtuallogical blocks of a file based virtual memory to be used by the VM. Theapparatus may also include a VM component for execution by the circuitryto enumerate a presence of the assigned allocated persistent memory forthe VM based on the EPT, create a virtual disk abstraction for the filebased virtual memory and enable the VM to use the EPT to directly accessthe assigned allocated persistent memory.

Example 2

The apparatus of example 1 may include the VMM component to cause the VMto shut down. For these examples, the host OS component may generate afile from data stored to the assigned allocated persistent memory. Thehost OS component may also cause a copy of the file to be stored at asecond host computing device arranged to support the VM.

Example 3

The apparatus of example 1, the VM component may include a guest BIOScapable of enumerating the presence of the assigned allocated persistentmemory based on information provided by the VMM component.

Example 4

The apparatus of example 3, the one or more memory devices may includenon-volatile memory maintained on at least one NVDIMM coupled with thehost computing device. For these examples, the information provided bythe VMM component may include information in an NFIT arranged based onthe ACPI specification, version 6.1.

Example 5

The apparatus of example 1, the VM component may include a guest OSkernel capable of creating the virtual disk abstraction for the filebased virtual memory and using the EPT to directly access the assignedallocated persistent memory.

Example 6

The apparatus of example 1 may also include the VM component to requestan additional allocation of persistent memory responsive to the VMaccessing second virtual logical blocks not mapped to the at least onephysical memory page. The VMM component may receive an indication thatthe host OS component has allocated the additional persistent memoryresponsive to the request. The VMM component may assign the additionalallocation of persistent memory to the VM. The VMM component may updatethe EPT to map at least one additional physical memory page maintainedby the at least one of the memory devices to the second virtual logicalblocks of the file based virtual memory. The VM component may update thevirtual disk abstraction for the file based virtual memory and mayenable the VM to use the updated EPT to directly access the assignedadditionally allocated persistent memory.

Example 7

The apparatus of example 1, the persistent memory maintained at the oneor more memory devices comprises the persistent memory capable ofstoring data structures such that the data structures continue to beaccessible after the data structures are created and following a powerloss to the one or more memory devices.

Example 8

The apparatus of example 1, the one or more memory devices may bemaintained on at least one DIMM coupled with the host computing device.

Example 9

The apparatus of example 1, the one or more memory devices may includevolatile or non-volatile memory.

Example 10

The apparatus of example 9, the volatile memory may include RAM, D-RAM,DDR SDRAM, SRAM, T-RAM or Z-RAM.

Example 11

The apparatus of example 9, the non-volatile memory may include phasechange memory that uses chalcogenide phase change material, flashmemory, ferroelectric memory, SONOS memory, polymer memory,ferroelectric polymer memory, FeTRAM, FeRAM, ovonic memory, nanowire,EEPROM, phase change memory, memristors or STT-MRAM.

Example 12

The apparatus of example 1 may also include one or more of: a networkinterface communicatively coupled to the apparatus; a battery coupled tothe apparatus; or a display communicatively coupled to the apparatus.

Example 13

An example method may include receiving, by circuitry at a hostcomputing device, an allocation of persistent memory maintained at oneor more memory devices coupled with the host computing device. For theseexamples, the persistent memory may be allocated to one or more VMshosted by the host computing device based on respective file basedvirtual memory to be used by the one or more VMs. The method may alsoinclude assigning at least a portion of the allocated persistent memoryto a VM from among the one or more VMs by creating an EPT to map atleast one physical memory page maintained by at least one of the memorydevices to first virtual logical blocks of a file based virtual memoryto be used by the VM. The method may also include providing informationto the VM for the VM to enumerate a presence of the assigned allocatedpersistent memory, create a virtual disk abstraction for the file basedvirtual memory and use the EPT to directly access the assigned allocatedpersistent memory.

Example 14

The method of example 13 may also include causing the VM to shut down.The method may also include generating a file from data stored to theassigned allocated persistent memory. The method may also includecopying the file to a second host computing device arranged to supportthe VM.

Example 15

The method of example 13, the persistent memory may be allocated by ahost OS for the host computing device.

Example 16

The method of example 15, the VM including a guest BIOS capable ofenumerating the presence of the assigned allocated persistent memorybased on the information provided to the VM.

Example 17

The method of example 16, the one or more memory devices includesnon-volatile memory maintained on at least one NVDIMM coupled with thehost computing device. For these examples, the information provided byto the VM may include information include in an NFIT arranged based onthe ACPI specification, version 6.1.

Example 18

The method of example 16, the VM may include a guest OS kernel capableof creating the virtual disk abstraction for the file based virtualmemory and using the EPT to directly access the assigned allocatedpersistent memory.

Example 19

The method of example 13 may also include receiving an additionalallocation of persistent memory responsive to the VM accessing secondvirtual logical blocks not mapped to the at least one physical memorypage. The method may also include assigning the additional allocation ofpersistent memory to the VM. The method may also include updating theEPT to map at least one additional physical memory page maintained bythe at least one of the memory devices to the second virtual logicalblocks of the file based virtual memory. The method may also includeproviding the updated EPT to the VM for the VM to update the virtualdisk abstraction for the file based virtual memory and for the VM to usethe updated EPT to directly access the assigned additionally allocatedpersistent memory.

Example 20

The method of example 13, the persistent memory maintained at the one ormore memory devices may include the persistent memory being capable ofstoring data structures such that the data structures continue to beaccessible after the data structures are created and following a powerloss to the one or more memory devices.

Example 21

The method of example 13, the one or more memory devices may bemaintained on at least one DIMM coupled with the host computing device.

Example 24

The method of example 13, the one or more memory devices may includevolatile or non-volatile memory.

Example 23

The method of example 22, the volatile memory may include (may includeRAM, D-RAM, DDR SDRAM, SRAM, T-RAM or Z-RAM.

Example 24

The method of example 22, the non-volatile memory may include phasechange memory that uses chalcogenide phase change material, flashmemory, ferroelectric memory, SONOS memory, polymer memory,ferroelectric polymer memory, FeTRAM, FeRAM, ovonic memory, nanowire,EEPROM, phase change memory, memristors or STT-MRAM.

Example 25

An example at least one machine readable medium may include a pluralityof instructions that in response to being executed by a system that maycause the system to carry out a method according to any one of examples13 to 24.

Example 26

An apparatus may include means for performing the methods of any one ofexamples 13 to 24.

Example 27

An example at least one machine readable medium may include a pluralityof instructions that in response to being executed by a system at a hostcomputing device may cause the system to receive an allocation ofpersistent memory maintained at one or more memory devices coupled withthe host computing device. For these examples, the persistent memoryallocated to one or more VMs hosted by the host computing device basedon respective file based virtual memory to be used by the one or moreVMs. The instructions may also cause the system to assign at least aportion of the allocated persistent memory to a VM from among the one ormore VMs by creating an EPT to map at least one physical memory pagemaintained by at least one of the memory devices to first virtuallogical blocks of a file based virtual memory to be used by the VM. Theinstructions may also cause the system to provide information to the VMfor the VM to enumerate a presence of the assigned allocated persistentmemory, create a virtual disk abstraction for the file based virtualmemory and use the EPT to directly access the assigned allocatedpersistent memory.

Example 28

The at least one machine readable medium of example 27, the instructionsmay further cause the system to cause the VM to shut down. Theinstructions may also cause the system to generate a file from datastored to the assigned allocated persistent memory. The instructions mayalso cause the system to copy the file to a second host computing devicearranged to support the VM.

Example 29

The at least one machine readable medium of example 27, the persistentmemory may be allocated by a host OS for the host computing device.

Example 30

The at least one machine readable medium of example 29, the VM mayinclude a guest BIOS capable of enumerating the presence of the assignedallocated persistent memory based on the information provided to the VM.

Example 31

The at least one machine readable medium of example 30, the one or morememory devices may include non-volatile memory maintained on at leastone NVDIMM coupled with the host computing device. For these examples,the information provided by to the VM may include information include inan NFIT arranged based on the ACPI specification, version 6.1.

Example 32

The at least one machine readable medium of example 30, the VM mayinclude a guest OS kernel capable of creating the virtual diskabstraction for the file based virtual memory and using the EPT todirectly access the assigned allocated persistent memory.

Example 33

The at least one machine readable medium of example 27, the instructionsmay further cause the system to receive an additional allocation ofpersistent memory responsive to the VM accessing second virtual logicalblocks not mapped to the at least one physical memory page. Theinstructions may also cause the system to assign the additionalallocation of persistent memory to the VM. The instructions may alsocause the system to update the EPT to map at least one additionalphysical memory page maintained by the at least one of the memorydevices to the second virtual logical blocks of the file based virtualmemory. The instructions may also cause the system to provide theupdated EPT to the VM for the VM to update the virtual disk abstractionfor the file based virtual memory and for the VM to use the updated EPTto directly access the assigned additionally allocated persistentmemory.

Example 34

The at least one machine readable medium of example 27, the persistentmemory maintained at the one or more memory devices may include thepersistent memory capable of storing data structures such that the datastructures continue to be accessible after the data structures arecreated and following a power loss to the one or more memory devices.

Example 35

The at least one machine readable medium of example 27, the one or morememory devices maintained on at least one DIMM coupled with the hostcomputing device.

Example 36

The at least one machine readable medium of example 27, the one or morememory devices may include volatile or non-volatile memory.

Example 37

The at least one machine readable medium of example 36, the volatilememory may include RAM, D-RAM, DDR SDRAM, SRAM, T-RAM or Z-RAM.

Example 38

The at least one machine readable medium of example 36, the non-volatilememory may include phase change memory that uses chalcogenide phasechange material, flash memory, ferroelectric memory, SONOS memory,polymer memory, ferroelectric polymer memory, FeTRAM, FeRAM, ovonicmemory, nanowire, EEPROM, phase change memory, memristors or STT-MRAM.

In the foregoing Detailed Description, it can be seen that variousfeatures are grouped together in a single example for the purpose ofstreamlining the disclosure. This method of disclosure is not to beinterpreted as reflecting an intention that the claimed examples requiremore features than are expressly recited in each claim. Rather, as thefollowing claims reflect, inventive subject matter lies in less than allfeatures of a single disclosed example. Thus the following claims arehereby incorporated into the Detailed Description, with each claimstanding on its own as a separate example. In the appended claims, theterms “including” and “in which” are used as the plain-Englishequivalents of the respective terms “comprising” and “wherein,”respectively. Moreover, the terms “first,” “second,” “third,” and soforth, are used merely as labels, and are not intended to imposenumerical requirements on their objects.

Although the subject matter has been described in language specific tostructural features and/or methodological acts, it is to be understoodthat the subject matter defined in the appended claims is notnecessarily limited to the specific features or acts described above.Rather, the specific features and acts described above are disclosed asexample forms of implementing the claims.

What is claimed is:
 1. An apparatus comprising: circuitry at a hostcomputing device, the circuitry to: allocate persistent memory, thepersistent memory composed of one or more memory devices coupled withthe host computing device, to one or more virtual machines (VMs), theVMs hosted by the host computing device based on respective file basedvirtual memory used by the one or more VMs; assign a portion of theallocated persistent memory to a VM from among the one or more VMs; map,by generation of an extended page table, at least one physical memorypage of the one or more memory devices to first virtual logical blocksof a file based virtual memory residing on a direct access storage (DAS)volume used by the VM; enumerate a presence of the assigned portion ofthe allocated persistent memory to the VM; and create a virtual diskabstraction corresponding to the file based virtual memory residing onthe DAS volume that enables the VM to directly access, via use of theextended page table, the one or more memory devices that correspond tothe assigned portion of the allocated persistent memory.
 2. Theapparatus of claim 1, comprising the circuitry to: cause the VM to shutdown; generate a file from data stored to the assigned portion of theallocated persistent memory; and cause a copy of the file to be storedat a second host computing device arranged to support the VM.
 3. Theapparatus of claim 1, the persistent memory maintained at the one ormore memory devices comprises the persistent memory capable to storedata structures such that the data structures continue to be accessibleafter the data structures are created and following a power loss to theone or more memory devices.
 4. The apparatus of claim 1, the one or morememory devices maintained on at least one dual in-line memory module(DIMM) coupled with the host computing device.
 5. The apparatus of claim1, wherein the one or more memory devices include volatile ornon-volatile memory, the volatile memory including random-access memory(RAM), Dynamic RAM (D-RAM), double data rate synchronous dynamic RAM(DDR SDRAM), static random-access memory (SRAM), thyristor RAM (T-RAM)or zero-capacitor RAM (Z-RAM) and the non-volatile memory includingphase change memory that uses chalcogenide phase change material, flashmemory, ferroelectric memory, silicon-oxide-nitride-oxide-silicon(SONOS) memory, polymer memory, ferroelectric polymer memory,ferroelectric transistor random access memory (FeTRAM or FeRAM), ovonicmemory, nanowire, electrically erasable programmable read-only memory(EEPROM), phase change memory, memristors or spin transfer torquemagnetoresistive random access memory (STT-MRAM).
 6. The apparatus ofclaim 1, wherein responsive to the VM accessing second virtual logicalblocks not mapped to the at least one physical memory page, thecircuitry to: request an additional allocation of persistent memory;assign the additional allocation of persistent memory to the VM; updatethe extended page table to map at least one additional physical memorypage of the one or more memory devices to the second virtual logicalblocks of the file based virtual memory; and update the virtual diskabstraction corresponding to the file based virtual memory residing onthe DAS volume and enable the VM to use the updated extended page tableto directly access the assigned additionally allocated persistentmemory.
 7. A method comprising: receiving, by circuitry at a hostcomputing device, an allocation of memory, the memory composed of one ormore non-volatile dual in-line memory modules (NVDIMMs) coupled with thehost computing device, the memory allocated to one or more virtualmachines (VMs), the VMs hosted by the host computing device based onrespective file based virtual memory used by the one or more VMs;assigning a portion of the allocated memory to a VM from among the oneor more VMs; mapping, by generating an extended page table, at least onephysical memory page of the one or more NVDIMMs to first virtual logicalblocks of a file based virtual memory residing on a direct accessstorage (DAS) volume used by the VM; enumerating a presence of theassigned portion of the allocated memory to the VM; and creating avirtual disk abstraction corresponding to the file based virtual memoryresiding on the DAS volume that enables the VM to directly access, usingof the extended page table, the one or more NVDIMMS that correspond tothe assigned portion of the allocated memory.
 8. The method of claim 7,comprising: causing the VM to shut down; generating a file from datastored to the assigned portion of the allocated memory; and copying thefile to a second host computing device arranged to support the VM. 9.The method of claim 7, comprising the memory allocated by a hostoperating system (OS) for the host computing device.
 10. The method ofclaim 9, comprising the VM including a guest basic input/output system(BIOS) capable of enumerating the presence of the assigned portion ofthe allocated memory to the VM based on information provided to the VMfrom the host OS.
 11. The method of claim 10, the information providedto the VM comprises information included in a NVDIMM firmware interfacetable (NFIT) arranged based on the ACPI specification, version 6.1. 12.The method of claim 10, comprising the VM including a guest OS kernelcapable of using the extended page table to directly access the assignedportion of the allocated memory.
 13. The method of claim 7, the memorycomposed of the one or more NVDIMMs comprises persistent memory.
 14. Themethod of claim 7, comprising the one or more NVDIMMs including phasechange memory that uses chalcogenide phase change material, flashmemory, ferroelectric memory, silicon-oxide-nitride-oxide-silicon(SONOS) memory, polymer memory, ferroelectric polymer memory,ferroelectric transistor random access memory (FeTRAM or FeRAM), ovonicmemory, nanowire, electrically erasable programmable read-only memory(EEPROM), phase change memory, memristors or spin transfertorque—magnetoresistive random access memory (STT-MRAM).
 15. The methodof claim 7, further comprising: receiving an additional allocation ofmemory responsive to the VM accessing second virtual logical blocks notmapped to the at least one physical memory page; assigning theadditional allocation of memory to the VM; updating the extended pagetable to map at least one additional physical memory page of by theNVDIMMs to the second virtual logical blocks of the file based virtualmemory; and providing the updated EPT to the VM for the VM to update thevirtual disk abstraction corresponding to the file based virtual memoryresiding on the DAS volume and enable the VM to use the updated extendedpage table to directly access the assigned additionally allocatedmemory.
 16. At least one non-transitory machine readable mediumcomprising a plurality of instructions that in response to beingexecuted by a system at a host computing device cause the system to:allocate memory, the memory composed of one or more non-volatile dualin-line memory modules (NVDIMMs) coupled with the host computing device,the memory allocated to one or more virtual machines (VMs), the VMshosted by the host computing device based on respective file basedvirtual memory to be used by the one or more VMs; assign a portion ofthe allocated memory to a VM from among the one or more VMs; map, bygeneration of an extended page table, at least one physical memory pageof the one or more NVDIMMs to first virtual logical blocks of a filebased virtual memory residing on a direct access storage (DAS) volumeused by the VM; enumerate a presence of the assigned portion of theallocated memory to the VM; and create a virtual disk abstractioncorresponding to the file based virtual memory residing on the DASvolume that enables the VM to directly access, using the extended pagetable, the one or more NVDIMMS that correspond to the assigned portionof the allocated memory.
 17. The at least one non-transitory machinereadable medium of claim 16, the instructions to further cause thesystem to: cause the VM to shut down; generate a file from data storedto the assigned portion of the allocated memory; and copy the file to asecond host computing device arranged to support the VM.
 18. The atleast one non-transitory machine readable medium of claim 17, the memorycomposed of at the one or more NVDIMMs comprises persistent memory. 19.The at least one non-transitory machine readable medium of claim 16,comprising the memory allocated by a host operating system (OS) for thehost computing device.
 20. The at least one non-transitory machinereadable medium of claim 19, comprising the VM to include a guest basicinput/output system (BIOS) capable of enumerating the presence of theassigned portion of the allocated memory to the VM based on informationprovided to the VM from the host OS.
 21. The at least one non-transitorymachine readable medium of claim 20, the information provided to the VMcomprises information included in a NVDIMM firmware interface table(NFIT) arranged based on the ACPI specification, version 6.1.
 22. The atleast one non-transitory machine readable medium of claim 20, comprisingthe VM to include a guest OS kernel capable of using the extended pagetable to directly access the assigned portion of the allocated memory.23. The at least one non-transitory machine readable medium of claim 16,the instructions to further cause the system to: receive an additionalallocation of memory responsive to the VM accessing second virtuallogical blocks not mapped to the at least one physical memory page;assign the additional allocation of memory to the VM; update theextended page table to map at least one additional physical memory pageof by the NVDIMMs to the second virtual logical blocks of the file basedvirtual memory; and provide the updated extended page table to the VMfor the VM to update the virtual disk abstraction corresponding to thefile based virtual memory residing on the DAS volume and enable the VMto use the updated extended page table to directly access the assignedadditionally allocated memory.